Fixes #21658: Fix OpenAPI schema for available-prefixes endpoint request body#21956
Merged
jnovinger merged 1 commit intonetbox-community:mainfrom Apr 20, 2026
Merged
Conversation
pheus
requested review from
a team and
jnovinger
and removed request for
a team
jnovinger
approved these changes
Apr 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes: #21658
Summary
The
available-prefixesendpoint correctly validates input usingPrefixLengthSerializer, which expects aprefix_lengthfield.However, the OpenAPI schema incorrectly documents the request body using
PrefixSerializer, which leads to a mismatch between the API documentation and the actual behavior.This change updates the OpenAPI schema to use
PrefixLengthSerializer, aligning the documentation with the implemented API behavior.